Skip to content

OBSDOCS-1722: Port "Troubleshooting log forwarding" to 5.8 and 6.y #89047

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
theashiot wants to merge 1 commit into from
Closed

OBSDOCS-1722: Port "Troubleshooting log forwarding" to 5.8 and 6.y #89047

theashiot wants to merge 1 commit into from

Conversation

@theashiot
Copy link
Contributor

@theashiot theashiot commented Feb 24, 2025 •
edited
Loading

Version(s): 4.17

Issue: https://issues.redhat.com/browse/OBSDOCS-1722

Link to docs preview:

QE review:

  • QE has approved this change.

Additional information:
Additional information: This PR only ports exiting and already published content to a newer release. Content enhancement is beyond the scope of the Jira/PR.

Existing published content: https://docs.openshift.com/container-platform/4.16/observability/logging/troubleshooting/log-forwarding-troubleshooting.html
Existing file that was copied: https://github.com/openshift/openshift-docs/blob/main/observability/logging/troubleshooting/log-forwarding-troubleshooting.adoc

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Feb 24, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Feb 24, 2025 •
edited by openshift-ci bot
Loading

@theashiot: This pull request references OBSDOCS-1722 which is a valid jira issue.

Details

In response to this:

Version(s): 4.17

Issue: https://issues.redhat.com/browse/OBSDOCS-1722

Link to docs preview:

QE review:

  • QE has approved this change.

Additional information:
Additional information: This PR only ports exiting and already published content to a newer release. Content enhancement is beyond the scope of the Jira/PR.

Existing published content: https://docs.openshift.com/container-platform/4.16/observability/logging/troubleshooting/log-forwarding-troubleshooting.html
Existing file that was copied: https://github.com/openshift/openshift-docs/blob/main/observability/logging/troubleshooting/log-forwarding-troubleshooting.adoc

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci openshift-ci bot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Feb 24, 2025
@ocpdocs-previewbot
Copy link

ocpdocs-previewbot commented Feb 24, 2025 •
edited
Loading

🤖 Tue Feb 25 14:20:40 - Prow CI generated the docs preview:
https://89047--ocpdocs-pr.netlify.app
Complete list of updated preview URLs: artifacts/updated_preview_urls.txt

@openshift-ci-robot
Copy link

openshift-ci-robot commented Feb 24, 2025 •
edited by openshift-ci bot
Loading

@theashiot: This pull request references OBSDOCS-1722 which is a valid jira issue.

Details

In response to this:

Version(s): 4.17

Issue: https://issues.redhat.com/browse/OBSDOCS-1722

Link to docs preview:

QE review:

  • QE has approved this change.

Additional information:
Additional information: This PR only ports exiting and already published content to a newer release. Content enhancement is beyond the scope of the Jira/PR.

Existing published content: https://docs.openshift.com/container-platform/4.16/observability/logging/troubleshooting/log-forwarding-troubleshooting.html
Existing file that was copied: https://github.com/openshift/openshift-docs/blob/main/observability/logging/troubleshooting/log-forwarding-troubleshooting.adoc

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci openshift-ci bot added size/L Denotes a PR that changes 100-499 lines, ignoring generated files. and removed size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels Feb 25, 2025
@openshift-ci
Copy link

openshift-ci bot commented Feb 25, 2025

@theashiot: all tests passed!

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@openshift-merge-robot
Copy link

openshift-merge-robot commented Feb 28, 2025

PR needs rebase.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Feb 28, 2025
@openshift-bot
Copy link

openshift-bot commented May 29, 2025

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci openshift-ci bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 29, 2025
@openshift-bot
Copy link

openshift-bot commented Jun 29, 2025

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

@openshift-ci openshift-ci bot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jun 29, 2025
@theashiot theashiot closed this Jul 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

5 participants

@theashiot @openshift-ci-robot @ocpdocs-previewbot @openshift-merge-robot @openshift-bot